|
On-Device Portals (ODPs) allow mobile phone users to easily browse, purchase and use mobile content and services. An ODP platform enables operators to provide a consistent and branded on-device experience across their broadening portfolio of services and typically provides on-device catalogs of content for purchase, deep links to WAP portals, customer care functionality and rich media services such as full track music, TV and video. A key benefit of on-device portals is the ability to target the user rather than the device itself. This personalized service delivery, coupled with the ability to be updated on a frequent basis by the operator – refining services or adding new content – makes ODPs an attractive proposition that has already proven successful in encouraging users to access mobile content.〔Operators in fresh effort to promote mobile surfing, Financial Times' Digital Business Supplement, April 18, 2007〕 By enhancing the user experience, ODPs improve customer satisfaction, reduce churn and in turn, drive higher data revenues. On-Device Portals generally offer the following applications: Offline portal, store front, home-screen replacement and reporting function: * Offline Portal - An application that allows the user to browse content categories and preview content free of charge through pre-cached content that doesn’t require a WAP connection and creates a mobile environment that blurs offline and online experiences. * Store Front - A client-server application enabling the user to discover, preview and select cached content offline, before accessing it via a WAP link. * Home-Screen Replacement - A dashboard function of the ODP client that replaces the handset’s home screen to provide zero click access to customized mobile content and services. * Reporting Function - User analytics that allow operators to measure, refine and improve the delivery of data services by providing visibility into the way subscribers use and interact with their mobile devices. On-Device Portals can be targeted to a specific mobile operating system or provide multi-platform support allowing operators to achieve a consistent, branded experience across of all devices whether they run on Symbian (Symbian OS), Microsoft (Windows Mobile), BREW (Binary Runtime Environment for Wireless), Java or Research in Motion (RIM) platforms. Some vendors have server-side components to their On-Device Portal offerings which are tied into operator billing systems that deliver features such as usage tracking and lifecycle management. On-Device Portals are not intended to replace the operating system (OS) or other aspects of the phone’s interface.〔On-Device Portals, ARCchart Ltd., January 2006〕 The term On-Device Portal was coined by the London-based ARCchart Research in 2001. In 2005, ARCchart estimated 10 million ODP-enabled units were in the marketplace. == History of On-Device Portals == On-Device Portal technology emerged in 2000, as operating systems and Java were beginning to be deployed on mobile handsets. One.Tel launched smart on device applications using a combination of Java and SIMtoolkit technology in May 2000. In 2002, four vendors — ActiveSky, SurfKitchen, Action Engine and Trigenix - began developing ODP offerings. In March 2003 at CeBIT O2 demonstrated an ActiveSky powered O2 branded On-Device portal that was both user and operator (remotely) reconfigurable, that same year KDDI deployed an ActiveSky based solution. In 2003, operators including O2, Sonofon and ONE began to deploy ODP solutions. From 2001 to 2005, it was central to many MVNO solutions, as a more cost effective and customer-centric alternative to handset software variants or SIM toolkits, Virtuser developed many trials of these, including a pre-blackberry email service that used Bluetooth in buildings. Since 2003, On-Device Portal technology has been embraced by mobile operators across the world〔 to compliment WAP-based mobile data services and help operators deliver on the promise of mobile data services. Carriers expected the launch of High-Speed Downlink Packet Access (HSDPA), in which they had invested heavily, to drive robust average revenue per user (ARPU) growth. But despite this investment, the mobile data services market still only represented 19% of global mobile service revenue in 2007.〔Mobile data revenue will double by 2012, Dan Locke, Analyst, Pyramid Research, April 14, 2008〕 Several factors have been cited for the slow uptake in data services, but poor user experience, based on older browser-based WAP technology, is widely acknowledged as one of the leading reasons. The browser-based mobile experience is considered difficult and complex, often requiring a user to click multiple times in order to navigate from browsing to downloading or purchasing content. Separately, WAP’s structure, which differs from HTML, has made it difficult for content developers to build efficient content channels. The On-device portal is also not without complications, supporting wide handset lists is a lot harder to manage than mobile web content, and updating major components is not just a case of re-publishing, but of redistributing applications. At the same time, while it is generally easy to test web content on a handful of browsers, portals need to be tested on nearly every handset which will be expected to use the on-device portal. 抄文引用元・出典: フリー百科事典『 ウィキペディア（Wikipedia）』 ■ウィキペディアで「On-Device Portal」の詳細全文を読む スポンサード リンク
|